You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes SENTRY-FOR-SENTRY-7MET. The issue was that: Missing index on sentry_grouprulestatus.date_added forces full table scan, exceeding database statement timeout.
Adds an index to the date_added field in the GroupRuleStatus model.
Creates a new migration to alter the date_added field and add the db_index=True property.
This fix was generated by Seer in Sentry, triggered by [email protected]. 👁️ Run ID: 115
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Add Database Index to date_added Field on GroupRuleStatus Model
This pull request addresses a database performance issue caused by the lack of an index on the date_added field in the GroupRuleStatus model, which resulted in full table scans and statement timeouts. The solution introduces the db_index=True attribute to the date_added field in src/sentry/models/grouprulestatus.py and adds a corresponding Django migration to apply this schema change in a post-deployment safe manner.
Key Changes
• Modified the date_added field in GroupRuleStatus to add db_index=True.
• Added migration file src/sentry/migrations/0996_add_grouprulestatus_date_added_idx.py to apply the index change in a post-deployment step.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes SENTRY-FOR-SENTRY-7MET. The issue was that: Missing index on
sentry_grouprulestatus.date_addedforces full table scan, exceeding database statement timeout.date_addedfield in theGroupRuleStatusmodel.date_addedfield and add thedb_index=Trueproperty.This fix was generated by Seer in Sentry, triggered by [email protected]. 👁️ Run ID: 115
Not quite right? Click here to continue debugging with Seer.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Copied from getsentry#101080
Original PR: getsentry#101080